Enabling parallel websphere runtime versions

ABSTRACT

A computer implemented method, a tangible storage medium, and a data processing system build a runtime environment of a system. A profile manager receives a service request containing a profile identifier. The profile identifier specifies a required version of at least one software component. The profile manager identifies a complete installation of the software component, and at least one delta file. The profile manager dynamically constructs a classpath for the required version by preferentially utilizing files from the at least one delta file followed by files from the complete installation. The runtime environment is then built utilizing the classpath.

This application is a continuation of application Ser. No. 12/465,282,filed May 13, 2009, status pending.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to the data processing fieldand, more specifically, to a computer implemented method, apparatus andcomputer program product for building a runtime environment of a systemcontaining a plurality of different versions of at least one softwarecomponent.

2. Description of the Related Art

When an enterprise application server (EAS) in a production system isupdated, most fix pack installation software will completely upgrade theenterprise application server as a whole. In particular, all theprofiles or server runtimes are upgraded to the latest fix pack version,and they will all run at the same enterprise application server fix packlevel. There are no provisions to install and maintain different fixpack versions in the same machine.

Assume, for example, that an enterprise application server base version,for example, an IBM WebSphere® Application Server (WAS) version 6.1, isbeing installed on a system. Assume also that three different runtimeenvironments (REs), for example, WAS profiles X, Y and Z, exist on theenterprise application server, and that there are also three differentapplications: deployed on the X, Y and Z profiles, for example, TEST1 onprofile X, TEST2 on profile Y, and TEST3 on profile Z. Assume also thatit is it required to upgrade the EAS from one version to another, forexample, from WAS version 6.1 to WAS version 6.1.0.25, only forapplication TEST2 deployed on runtime environment Y, and that it is notrequired to upgrade the EAS for the other applications. The upgrade, infact, might even have a negative impact to one or both of applicationsTEST1 and TEST3. For example, application TEST1 may have been developedspecifically to use the interface provided by IBM WebSphere® ApplicationServer version 6.1.

Current patch upgrades for enterprise applications generally upgrade thecomplete enterprise application server. There are no provisions toupgrade only one or more particular runtime environments of anenterprise application server so that different runtime environments canrun at different fix pack levels which are relevant to the applicationsdeployed on the runtime environments. Current runtime environments alsorequire that the base enterprise application server be running andcompletely rely on the base enterprise application server files. They donot have an option of selecting the version of interest, for example,profile X, which exists on system s1 may want to run on IBM WebSphere®Application Server 6.1, whereas profile Y on the same system s1 may wantto run on IBM WebSphere® Application Server 6.1.5.

BRIEF SUMMARY OF THE INVENTION

According to one embodiment of the present invention, a computerimplemented method, a tangible storage medium, and a data processingsystem are provided for building a runtime environment of a system. Aprofile manager receives a service request containing a profileidentifier. The profile identifier specifies a required version of atleast one software component. The profile manager identifies a completeinstallation of the software component, and at least one delta file. Theprofile manager dynamically constructs a classpath for the requiredversion by preferentially utilizing files from the at least one deltafile followed by files from the complete installation. The runtimeenvironment is then built utilizing the classpath.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 depicts a pictorial representation of a network of dataprocessing systems in which illustrative embodiments may be implemented;

FIG. 2 is a block diagram of a data processing system in whichillustrative embodiments may be implemented;

FIG. 3 is a block diagram illustrating the relationship of softwarecomponents operating within a computer system that may implement thepresent invention;

FIG. 4 is a block diagram of a Java® virtual machine in accordance witha illustrative embodiment;

FIG. 5 is a current known dataflow diagram for provisioning profiles toa Java® virtual machine of a data processing system;

FIG. 6 is a dataflow diagram for provisioning profiles to a Java®virtual machine of a data processing system according to an illustrativeembodiment;

FIG. 7 is a block diagram that schematically illustrates an Enterpriseapplication server file system structure according to the prior art;

FIG. 8 is a block diagram that schematically illustrates an Enterpriseapplication server file system structure according to an illustrativeembodiment;

FIG. 9 is a block diagram that schematically illustrates an installationof an Enterprise application server upgrade, patch, or fixpack accordingto an illustrative embodiment; and

FIG. 10 is a flowchart that schematically illustrates a method forselecting a system version by runtime environments according to anillustrative embodiment.

DETAILED DESCRIPTION OF THE INVENTION

As will be appreciated by one skilled in the art, the present inventionmay be embodied as a system, method or computer program product.Accordingly, the present invention may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,the present invention may take the form of a computer program productembodied in any tangible medium of expression having computer usableprogram code embodied in the medium.

Any combination of one or more computer usable or computer readablemedium(s) may be utilized. The computer-usable or computer-readablemedium may be, for example but is not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, device, or propagation medium. More specific examples (anon-exhaustive list) of the computer-readable medium would include thefollowing: an electrical connection having one or more wires, a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), an optical fiber, a portable compact disc read-onlymemory (CDROM), an optical storage device, a transmission media such asthose supporting the Internet or an intranet, or a magnetic storagedevice. Note that the computer-usable or computer-readable medium couldeven be paper or another suitable medium upon which the program isprinted, as the program can be electronically captured, via, forinstance, optical scanning of the paper or other medium, then compiled,interpreted, or otherwise processed in a suitable manner, if necessary,and then stored in a computer memory. In the context of this document, acomputer-usable or computer-readable medium may be any medium that cancontain, store, communicate, propagate, or transport the program for useby or in connection with the instruction execution system, apparatus, ordevice. The computer-usable medium may include a propagated data signalwith the computer-usable program code embodied therewith, either inbaseband or as part of a carrier wave. The computer usable program codemay be transmitted using any appropriate medium, including but notlimited to wireless, wireline, optical fiber cable, RF, etc.

Computer program code for carrying out operations of the presentinvention may be written in any combination of one or more programminglanguages, including an object oriented programming language such asJava®, Smalltalk, C++ or the like and conventional proceduralprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

The present invention is described below with reference to flowchartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products according to embodiments of the invention. Itwill be understood that each block of the flowchart illustrations and/orblock diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerprogram instructions.

These computer program instructions may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer program instructions may also bestored in a computer-readable medium that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablemedium produce an article of manufacture including instruction meanswhich implement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions which execute on the computer or other programmableapparatus provide processes for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

With reference now to the figures and in particular with reference toFIGS. 1-2, exemplary diagrams of data processing environments areprovided in which illustrative embodiments may be implemented. It shouldbe appreciated that FIGS. 1-2 are only exemplary and are not intended toassert or imply any limitation with regard to the environments in whichdifferent embodiments may be implemented. Many modifications to thedepicted environments may be made.

FIG. 1 depicts a pictorial representation of a network of dataprocessing systems in which illustrative embodiments may be implemented.Network data processing system 100 is a network of computers in whichthe illustrative embodiments may be implemented. Network data processingsystem 100 contains network 102, which is the medium used to providecommunications links between various devices and computers connectedtogether within network data processing system 100. Network 102 mayinclude connections, such as wire, wireless communication links, orfiber optic cables.

In the depicted example, server 104 and server 106 connect to network102 along with storage unit 108. In addition, clients 110, 112, and 114connect to network 102. Clients 110, 112, and 114 may be, for example,personal computers or network computers. In the depicted example, server104 provides information, such as boot files, operating system images,and applications to clients 110, 112, and 114. Clients 110, 112, and 114are clients to server 104 in this example. Network data processingsystem 100 may include additional servers, clients, and other devicesnot shown.

Program code located in network data processing system 100 may be storedon a computer recordable storage medium and downloaded to a dataprocessing system or other device for use. For example, program code maybe stored on a computer recordable storage medium on server 104 anddownloaded to client 110 over network 102 for use on client 110.

In the depicted example, network data processing system 100 is theInternet with network 102 representing a worldwide collection ofnetworks and gateways that use the Transmission ControlProtocol/Internet Protocol (TCP/IP) suite of protocols to communicatewith one another. At the heart of the Internet is a backbone ofhigh-speed data communication lines between major nodes or hostcomputers, consisting of thousands of commercial, governmental,educational and other computer systems that route data and messages. Ofcourse, network data processing system 100 also may be implemented as anumber of different types of networks, such as for example, an intranet,a local area network (LAN), or a wide area network (WAN). FIG. 1 isintended as an example, and not as an architectural limitation for thedifferent illustrative embodiments.

With reference now to FIG. 2, a block diagram of a data processingsystem is shown in which illustrative embodiments may be implemented.Data processing system 200 is an example of a computer, such as server104 or client 110 in FIG. 1, in which computer usable program code orinstructions implementing the processes may be located for theillustrative embodiments. In this illustrative example, data processingsystem 200 includes communications fabric 202, which providescommunications between processor unit 204, memory 206, persistentstorage 208, communications unit 210, input/output (I/O) unit 212, anddisplay 214.

Processor unit 204 serves to execute instructions for software that maybe loaded into memory 206. Processor unit 204 may be a set of one ormore processors or may be a multi-processor core, depending on theparticular implementation. Further, processor unit 204 may beimplemented using one or more heterogeneous processor systems in which amain processor is present with secondary processors on a single chip. Asanother illustrative example, processor unit 204 may be a symmetricmulti-processor system containing multiple processors of the same type.

Memory 206 and persistent storage 208 are examples of storage devices216. A storage device is any piece of hardware that is capable ofstoring information, such as, for example without limitation, data,program code in functional form, and/or other suitable informationeither on a temporary basis and/or a permanent basis. Memory 206, inthese examples, may be, for example, a random access memory or any othersuitable volatile or non-volatile storage device. Persistent storage 208may take various forms depending on the particular implementation. Forexample, persistent storage 208 may contain one or more components ordevices. For example, persistent storage 208 may be a hard drive, aflash memory, a rewritable optical disk, a rewritable magnetic tape, orsome combination of the above. The media used by persistent storage 208also may be removable. For example, a removable hard drive may be usedfor persistent storage 208.

Communications unit 210, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 210 is a network interface card. Communications unit210 may provide communications through the use of either or bothphysical and wireless communications links.

Input/output unit 212 allows for input and output of data with otherdevices that may be connected to data processing system 200. Forexample, input/output unit 212 may provide a connection for user inputthrough a keyboard, a mouse, and/or some other suitable input device.Further, input/output unit 212 may send output to a printer. Display 214provides a mechanism to display information to a user.

Instructions for the operating system, applications and/or programs maybe located in storage devices 216, which are in communication withprocessor unit 204 through communications fabric 202. In theseillustrative examples the instruction are in a functional form onpersistent storage 208. These instructions may be loaded into memory 206for execution by processor unit 204. The processes of the differentembodiments may be performed by processor unit 204 using computerimplemented instructions, which may be located in a memory, such asmemory 206.

These instructions are referred to as program code, computer usableprogram code, or computer readable program code that may be read andexecuted by a processor in processor unit 204. The program code in thedifferent embodiments may be embodied on different physical or tangiblecomputer readable media, such as memory 206 or persistent storage 208.

Program code 218 is located in a functional form on computer readablemedia 220 that is selectively removable and may be loaded onto ortransferred to data processing system 200 for execution by processorunit 204. Program code 218 and computer readable media 220 form computerprogram product 222 in these examples. In one example, computer readablemedia 220 may be in a tangible form, such as, for example, an optical ormagnetic disc that is inserted or placed into a drive or other devicethat is part of persistent storage 208 for transfer onto a storagedevice, such as a hard drive that is part of persistent storage 208. Ina tangible form, computer readable media 218 also may take the form of apersistent storage, such as a hard drive, a thumb drive, or a flashmemory that is connected to data processing system 200. The tangibleform of computer readable media 220 is also referred to as computerrecordable storage media. In some instances, computer readable media 220may not be removable.

Alternatively, program code 218 may be transferred to data processingsystem 200 from computer readable media 220 through a communicationslink to communications unit 210 and/or through a connection toinput/output unit 212. The communications link and/or the connection maybe physical or wireless in the illustrative examples. The computerreadable media also may take the form of non-tangible media, such ascommunications links or wireless transmissions containing the programcode.

In some illustrative embodiments, program code 218 may be downloadedover a network to persistent storage 208 from another device or dataprocessing system for use within data processing system 200. Forinstance, program code stored in a computer readable storage medium in aserver data processing system may be downloaded over a network from theserver to data processing system 200. The data processing systemproviding program code 218 may be a server computer, a client computer,or some other device capable of storing and transmitting program code218.

The different components illustrated for data processing system 200 arenot meant to provide architectural limitations to the manner in whichdifferent embodiments may be implemented. The different illustrativeembodiments may be implemented in a data processing system includingcomponents in addition to or in place of those illustrated for dataprocessing system 200. Other components shown in FIG. 2 can be variedfrom the illustrative examples shown. The different embodiments may beimplemented using any hardware device or system capable of executingprogram code. As one example, the data processing system may includeorganic components integrated with inorganic components and/or may becomprised entirely of organic components excluding a human being. Forexample, a storage device may be comprised of an organic semiconductor.

As another example, a storage device in data processing system 200 isany hardware apparatus that may store data. Memory 206, persistentstorage 208 and computer readable media 220 are examples of storagedevices in a tangible form.

In another example, a bus system may be used to implement communicationsfabric 202 and may be comprised of one or more buses, such as a systembus or an input/output bus. Of course, the bus system may be implementedusing any suitable type of architecture that provides for a transfer ofdata between different components or devices attached to the bus system.Additionally, a communications unit may include one or more devices usedto transmit and receive data, such as a modem or a network adapter.Further, a memory may be, for example, memory 206 or a cache such asfound in an interface and memory controller hub that may be present incommunications fabric 202.

With reference now to FIG. 3, a block diagram illustrates therelationship of software components operating within a computer systemthat may implement the present invention. Java®-based system 300contains platform specific operating system 302 that provides hardwareand system support to software executing on a specific hardwareplatform. Java® virtual machine (JVM) 304 is one software applicationthat may execute in conjunction with the operating system. Java® virtualmachine 304 provides a Java® run-time environment with the ability toexecute Java® application/applet 306, which is a program, servlet, orsoftware component written in the Java® programming language. Thecomputer system in which Java® virtual machine 304 operates may besimilar to data processing system 200 or computer 100 described above.However, Java® virtual machine 304 may be implemented in dedicatedhardware on a so-called Java® chip, Java®-on-silicon, or Java® processorwith an embedded picoJava core.

At the center of a Java® run-time environment is the Java® virtualmachine, which supports all aspects of Java®'s environment, includingits architecture, security features, and mobility across networks, andplatform independence.

The Java® virtual machine is a virtual computer, for example, a computerthat is specified abstractly. The specification defines certain featuresthat every Java® virtual machine must implement, with some range ofdesign choices that may depend upon the platform on which the Java®virtual machine is designed to execute. For example, all Java® virtualmachines must execute Java® bytecodes and may use a range of techniquesto execute the instructions represented by the bytecodes. A Java®virtual machine may be implemented completely in software or somewhat inhardware. This flexibility allows different Java° virtual machines to bedesigned for mainframe computers and PDAs.

The Java® virtual machine is the name of a virtual computer componentthat actually executes Java® programs. Java® programs are not rundirectly by the central processor but instead by the Java® virtualmachine, which is itself a piece of software running on the processor.The Java® virtual machine allows Java® programs to be executed on adifferent platform as opposed to only the one platform for which thecode was compiled. Java® programs are compiled for the Java® virtualmachine. In this manner, Java® is able to support applications for manytypes of data processing systems, which may contain a variety of centralprocessing units and operating systems architectures. To enable a Java®application to execute on different types of data processing systems, acompiler typically generates an architecture-neutral file format. Thiscompiled code is executable on many processors, given the presence ofthe Java® run-time system. The Java® compiler generates bytecodeinstructions that are nonspecific to a particular computer architecture.A bytecode is a machine independent code generated by the Java° compilerand executed by a Java° interpreter. A Java° interpreter is part of theJava° virtual machine that alternately decodes and interprets a bytecodeor bytecodes. These bytecode instructions are designed to be easy tointerpret on any computer and easily translated on the fly into nativemachine code. Byte codes may be translated into native code by ajust-in-time (JIT) compiler.

A Java® virtual machine loads class files and executes the bytecodeswithin them. The class files are loaded by a class loader in the Java®virtual machine. The class loader loads class files from an applicationand the class files from the Java® application programming interfaces(APIs) which are needed by the application. The execution engine thatexecutes the bytecodes may vary across platforms and implementations.

One type of software-based execution engine is a just-in-time compiler.With this type of execution, the bytecodes of a method are compiled tonative machine code upon successful fulfillment of some type of criteriafor jitting a method. The native machine code for the method is thencached and reused upon the next invocation of the method. The executionengine may also be implemented in hardware and embedded on a chip sothat the Java® bytecodes are executed natively. Java® virtual machinesusually interpret bytecodes, but Java® virtual machines may also useother techniques, such as just-in-time compiling, to execute bytecodes.

When an application is executed on a Java® virtual machine that isimplemented in software on a platform-specific operating system, a Java®application may interact with the host operating system by invokingnative methods. A Java® method is written in the Java° language,compiled to bytecodes, and stored in class files. A native method iswritten in some other language and compiled to the native machine codeof a particular processor. Native methods are stored in a dynamicallylinked library whose exact form is platform specific.

With reference now to FIG. 4, a block diagram of a Java® virtual machineis depicted in accordance with a illustrative embodiment. Java® virtualmachine (JVM) 400 includes class loader subsystem 402, which is amechanism for loading types, such as classes and interfaces, given fullyqualified names. Java® virtual machine 400 also contains runtime dataareas 404, execution engine 406, native method interface 408, and memorymanagement 410. Execution engine 406 is a mechanism for executinginstructions contained in the methods of classes loaded by class loadersubsystem 402. Execution engine 406 may be, for example, Java®interpreter 412 or just-in-time compiler 414. Native method interface408 allows access to resources in the underlying operating system.Native method interface 408 may be, for example, the Java® NativeInterface (JNI).

Runtime data areas 404 contain native method stacks 416, Java® stacks418, PC registers 420, method area 422, and heap 424. These differentdata areas represent the organization of memory needed by Java® virtualmachine 400 to execute a program.

Java® stacks 418 are used to store the state of Java® methodinvocations. When a new thread is launched, the Java® virtual machinecreates a new Java® stack for the thread. The Java° virtual machineperforms only two operations directly on Java° stacks. It pushes andpops frames. A thread's Java® stack stores the state of Java® methodinvocations for the thread. The state of a Java® method invocationincludes its local variables, the parameters with which it was invoked,its return value, if any, and intermediate calculations. Java® stacksare composed of stack frames. A stack frame contains the state of asingle Java® method invocation. When a thread invokes a method, theJava® virtual machine pushes a new frame onto the Java® stack of thethread. When the method completes, the Java® virtual machine pops theframe for that method and discards it. The Java® virtual machine doesnot have any registers for holding intermediate values; any Java®instruction that requires or produces an intermediate value uses thestack for holding the intermediate values. In this manner, the Java®instruction set is well-defined for a variety of platform architectures.

Program counter (PC) registers 420 are used to indicate the nextinstruction to be executed. Each instantiated thread gets its own PCregister and Java® stack. If the thread is executing a Java® virtualmachine method, the value of the PC register indicates the nextinstruction to execute. If the thread is executing a native method, thenthe contents of the PC register are undefined.

Native method stacks 416 stores the state of invocations of nativemethods. The state of native method invocations is stored in animplementation-dependent way in native method stacks, registers, orother implementation-dependent memory areas. In some Java® virtualmachine implementations, native method stacks 416 and Java® stacks 418are combined.

Method area 422 contains class data while heap 424 contains allinstantiated objects. The constant pool is located in method area 422 inthese examples. The Java® virtual machine specification strictly definesdata types and operations. Most Java® virtual machines choose to haveone method area and one heap, each of which are shared by all threadsrunning inside the Java® virtual machine, such as Java® virtual machine400. When Java® virtual machine 400 loads a class file, it parsesinformation about a type from the binary data contained in the classfile. Java° virtual machine 400 places this type of information into themethod area. Each time a class instance or array is created, the memoryfor the new object is allocated from heap 424. Java® virtual machine 400includes an instruction that allocates memory space within the memoryfor heap 424 but includes no instruction for freeing that space withinthe memory. Memory management 410 in the depicted example manages memoryspace within the memory allocated to heap 424. Memory management 410 mayinclude a garbage collector, which automatically reclaims memory used byobjects that are no longer referenced. Additionally, a garbage collectoralso may move objects to reduce heap fragmentation.

The illustrative embodiments herein describe a computer implementedmethod, a tangible storage medium, and a data processing system forbuilding a runtime environment of a system. A profile manager receives aservice request containing a profile identifier. The profile identifierspecifies a required version of at least one software component. Theprofile manager identifies a complete installation of the softwarecomponent, and at least one delta file. The profile manager dynamicallyconstructs a classpath for the required version by preferentiallyutilizing files from the at least one delta file followed by files fromthe complete installation. The runtime environment is then builtutilizing the classpath.

Illustrative embodiments provide a computer implemented method, systemand computer program product for an application/profile to select aruntime environment version during runtime. According to an illustrativeembodiment, an Enterprise application server fix pack upgrade functionslike a virtual installation and does not upgrade the Enterpriseapplication server version as a whole. Instead, both a current versionand the newer version should be present in the system after the upgradesuch that either version can be selected during application startup orthe profile startup phase.

According to a further illustrative embodiment, different runtimeversions, including the base version and upgraded versions are kept inthe system and are loaded dynamically based on the runtime election.

Referring now to FIG. 5, a known dataflow diagram for provisioningprofiles to a Java® virtual machine of a data processing system isdepicted. Java® virtual machine 510 is a Java® virtual machine such asJava® virtual machine 400 of FIG. 4. Java® virtual machine 510 installsand maintains different versions of the Enterprise application server inseparate profiles of the same machine by maintaining completeinstallations for each of the separate profiles.

Java® virtual machine 510 contains application servers 512-516.Application servers 512-516 are the primary runtime component whereapplications of Java® virtual machine 510 actually execute.

Each of application servers 512-516 executes one of Java® virtualmachine instances 518-522. Java® virtual machine instances 518-522 areclass instances within Java® virtual machine 510. Several of Java®virtual machine instances 518-522 can separately execute within Java®virtual machine 510, so long as those instances are each containedwithin a separate application server, such as application servers512-516.

Java® virtual machine instances 518-522 are created using one ofprofiles 524-528, stored in profile database 530. Profile database 529is a data structure implemented on a storage unit, such as storage unit108 of FIG. 1, that contains or references the location of profiles524-528. Profiles 524-528 are separate data partitions that include thefiles that define a runtime environment for an application serverprocess, such as a deployment manager or an application server. Eachruntime environment has its own configuration files, logs, properties,and other attributes. Profiles 524-528 can make each runtime ofapplication servers 512-516 unique and separate from the server binariesand from other profiles.

Each of profiles 524-528 is a complete enterprise application serverinstallation, including any software patches and updates available atthe time of which the profile is created. Each time one of profiles524-528 is patched or updated, a new, separate profile is created.Therefore, in one illustrative embodiment, profile 524 is a completeinstallation of a milestone release of the enterprise applicationserver. Profile 526 is a complete installation of the enterpriseapplication server. Profile 526 is also a patched version of profile524. Profile 528 is a complete installation of the Enterpriseapplication server. Profile 528 is also a patched version of profile526.

When Java® virtual machine 510 receives service request 530, profilemanager 532 recognizes profile identifier 534. Profile identifier 534 isan indication of which version of the enterprise application servershould be used to fulfill the request, and therefore which of profiles524-528 should be utilized in creating a particular instance, such asone of Java® virtual machine instances 518-522. Profile manager 532 thenretrieves the indicated one of profiles 524-528, and allocates thatretrieved profile to the particular one of application servers 512-516that is executing the instance.

Referring now to FIG. 6, a dataflow diagram for provisioning profiles toa Java® virtual machine of a data processing system is shown accordingto an illustrative embodiment. Java® virtual machine 610 is a Java®virtual machine such as Java® virtual machine 400 of FIG. 4. Java®virtual machine 610 installs and maintains different versions of theEnterprise application server and in the same machine separate profilesby maintaining delta files for each of the separate profiles.

Java® virtual machine 610 contains application servers 612-616.Application servers 612-616 are the primary runtime component whereapplications of Java® virtual machine 610 actually execute.

Each of application servers 612-616 executes one of Java® virtualmachine instances 618-622. Java® virtual machine instances 618-622 areclass instances within Java® virtual machine 610. Several of Java®virtual machine instances 618-622 can separately execute within Java®virtual machine 610, so long as those instances are each containedwithin a separate application server, such as application servers612-616.

Java® virtual machine instances 618-622 are created using one of profile624, and one or more of delta files 626-630, stored in profile database631. Profile database 631 is a data structure implemented on a storageunit, such as storage unit 108 of FIG. 1, that contains or referencesthe location of profile 624. Profile 624 is a separate data partitionthat includes the files that define a runtime environment for anapplication server process, such as a deployment manager or anapplication server. Each runtime environment has its own configurationfiles, logs, properties, and other attributes. Profile 624 can make eachruntime of application servers 612-616 unique and separate from theserver binaries and from other profiles.

Profile 624 is a complete enterprise application server installation.Unlike profiles 524-528 of FIG. 5, Profile 624 does not include anysoftware patches and updates available at the time of which the profileis created. In one illustrative embodiment, profile 624 is a completeinstallation of a milestone release of the Enterprise applicationserver.

Delta files 626-630 are files that contain either changes to a baseprofile, such as profile 624, or changes to a previous delta file, suchas others of delta files 626-630. For any software patch or update thatis to be applied to profile 624, the changes to be enacted to profile624 are not initially applied to profile 624, but instead saved as oneof delta files 626-630.

In one illustrative embodiment, each of delta files 626-630 is asoftware patch or update that contains changes to be enacted to profile624. When profile 624 is dynamically loaded into one of applicationservers 612-616, the classpath is constructed first with files from theidentified delta files 626-630, followed by files from the base profile624.

In one illustrative embodiment, each of delta files 626-630 is asequential software patch or update that contains changes to be enactedto profile 624 as modified by a previous one of delta files 626-630. Forexample, but not limited to, delta file 626 may be a first update toprofile 624, such that the software patch or update of delta file 626 isto be applied directly to profile 624. Delta file 628 may be asubsequent update to profile 624, such that the software patch or updateof delta file 628 is to be applied to profile 624 as modified by deltafile 626. Delta file 630 may be yet a further subsequent update toprofile 624, such that the software patch or update of delta file 628 isto be applied to profile 624 as modified by both delta file 626 anddelta file 628. Therefore, if service request 632 identifies a profileversion that includes each of delta files 626-630, the classpath isconstructed first with files from delta file 630, followed by files fromdelta file 628, followed by files from delta file 626, followed by filesfrom the base profile 624.

When Java® virtual machine 610 receives service request 632, profilemanager 634 recognizes profile identifier 636. Profile identifier 636 isan indication of which version of the Enterprise application servershould be used to fulfill the request, and therefore which of deltafiles 626-630 should be utilized along with profiles 624 in creating aparticular instance, such as one of Java® virtual machine instances618-622. Profile manager 634 then retrieves the indicated ones of deltafiles 626-630 along with profile 624, and allocates that retrievedprofile to the particular one of application servers 612-616 that isexecuting the instance.

Illustrative embodiments provide a computer implemented method, systemand computer program product for an application/profile to select aruntime environment version during runtime. According to an illustrativeembodiment, an Enterprise application server fix pack upgrade functionslike a virtual installation and does not upgrade the enterpriseapplication server version as a whole. Instead, both a current versionand the newer version should be present in the system after the upgradesuch that either version can be selected during application startup orthe profile startup phase.

According to a further illustrative embodiment, different runtimeversions, including the base version and upgraded versions are kept inthe system and are loaded dynamically based on the runtime election.

Referring now to FIG. 7, a block diagram that schematically illustratesan enterprise application server file system structure is shownaccording to the prior art. File structure 700 is an organization of thefile system structure of the EAS so that a base version and multipleother complete installations of the runtime files can be kept in theenterprise application server home directory. File structure 700 is aschematic representation of a file system containing profiles, such asprofiles 524-528 of FIG. 5.

File structure 700 includes a home directory 702. Home directory 702 canbe, for example, but is not limited to the \WebSphere\AppServer WAS_HOMEdirectory when the enterprise application server is a WebSphere®Application Server. Websphere® is a registered trademark ofInternational Business Machines Corporation. The \profiles directorylists the various profiles, however, the other directories and files ofWebSphere, for example, Java® directory 704, lib directory 706, pluginsdirectory 708 and properties file 710, are all at the WAS_HOME level.When an upgrade to the Enterprise application server is made, forexample, to upgrade from version 6.1.0.0 to version 6.1.0.25, each ofthe files, for example, files inside Java® directory 704, lib directory706, plugins directory 708 and properties file 710, will all be changedto reflect the upgrade.

If the upgrade to the Enterprise application server is saved as adifferent file name, then File structure 700 can maintain completecopies of both the upgraded Enterprise application server, and theoriginal enterprise application server. If the upgrade to the Enterpriseapplication server is not saved as a different file name, files for theoriginal version of the enterprise application server will be replacedand lost.

Referring now to FIG. 8, a block diagram that schematically illustratesan Enterprise application server file system structure is shownaccording to an illustrative embodiment. File structure 800 is anorganization the file system structure of the Enterprise applicationserver so that a base version and multiple other complete installationsof the runtime files can be kept in the enterprise application serverhome directory. File structure 800 is a schematic representation of afile system containing profiles and delta files, such as profiles 624and delta files 626-630 of FIG. 6.

File structure 800 includes a home directory 802. Home directory 802 canbe, for example, but is not limited to the \WebSphere\AppServer WAS_HOMEdirectory when the Enterprise application server is a WebSphere®Application Server. Websphere® is a registered trademark ofInternational Business Machines, Inc.

Home directory 802 initially contains version subdirectory 804. For eachpatch or software upgrade of enterprise application server that isinstalled, a new version subdirectory is added to home directory 802.Home directory 802 lists the various profiles. Each of the variousprofiles includes other files of the Enterprise application server, forexample, Java® directory 806, lib directory 808, plugins directory 810and properties file 812. The other files are installed at theWAS_HOME\Version_base_(—)6.1.0.0 level.

When an upgrade to the Enterprise application server is made, newversion subdirectory 814 is created. For example, an upgrade fromversion 6.1.0.0 to version 6.1.0.25, \version_base-6.1.0.0 directory isadded to contain the runtime directory files, such as, for example, butnot limited to Java® directory 816, lib directory 818, plugins directory820, and properties file 822, such that both version 6.1.0.0 and version6.1.0.25 are stored within the file system.

In one illustrative embodiment, the runtime directory files, such as,for example, but not limited to Java® directory 816, lib directory 818,plugins directory 820, and properties file 822, are delta files, such asone of delta files 624-628 of FIG. 6. The runtime directory files, suchas, for example, but not limited to Java® directory 816, lib directory818, plugins directory 820, and properties file 822 are changes to theEnterprise application server from the previous Java° directory 806, libdirectory 808, plugins directory 810 and properties file 812.

When a fixpack, patch, or upgrade is applied to the Enterpriseapplication server, the fixpack, patch, or upgrade can be either a“milestone upgrade” or a non-milestone” upgrade. If a “milestone”upgrade is selected, a new \version_delta_(—)6.1.0.25 is created thatcontains the updated set of files. For example, to upgrade from version6.1.0.0 to version 6.1.0.25, delta files for the runtime directory filesof version 6.1.0.0 for example, Java® directory 816, lib directory 818,plugins directory 820, and properties file 822, will be stored in newversion subdirectory 814.

A non-milestone installation is a complete installation of a completeversion level containing all of the file and directories of theEnterprise application server. In a non-milestone installation, theentire Enterprise application server system is upgraded to a newerversion. In contrast, a milestone installation is a partial installationof a version level that depends on one or more other installationdirectories and presumably at least one complete baseprofile/installation directory. In a milestone installation, the old andnew file versions are preserved. The new file versions are stored asdelta files, such as one of delta files 626-630 of FIG. 6.

If a “non-milestone” upgrade is selected, when the upgrade occurs, theruntime directory files, are simply overwritten such that only upgradedversion is present within the file structure.

When an application server, such as one of application servers 612-616of FIG. 6, is started, the Java® virtual machine instance is startedwith the proper profile. The classpath for the virtual machine instanceis constructed and contains files from version_delta_(—)6.1.0.25 first,followed by files from version_base_6.1.0.0. Some state data files, forexample, those in the properties subdirectory, may be replicated intheir entirety, if necessary, so that they are consistent. A particularprofile can be started in combination with a particular delta file. Theenterprise application server runtime, is backfilled with the baseprofile, or potentially, another delta file.

In this way, the ability to run a profile on a previous version of theEnterprise application server is preserved as well as on later versionswithout having to completely duplicate all the files.

FIG. 9 is a block diagram that schematically illustrates an installationof an Enterprise application server upgrade, patch, or fixpack accordingto an illustrative embodiment. Process 900 is a software process,executing on a software component, such as profile manager 634 of FIG.6.

Process 900 begins by starting the installer for installing the upgradedversion (Step 902). A determination is made whether the upgrade is amilestone upgrade (Step 904). Responsive to determining that the upgradeis a milestone upgrade (Yes output of Step 904), the upgrade isinstalled while retaining all previous versions of the files that areupdated by the upgrade (Step 906). Responsive to determining that theupgrade is not a milestone upgrade (No output of Step 904), the upgradeis installed such that the complete system of WAS is upgraded byreplacing files for previous versions with files for the upgradedversion (Step 908).

FIG. 10 is a flowchart that schematically illustrates a method forselecting a system version by runtime environments according to anillustrative embodiment. Process 1000 is a software method, executing ona software process, such as profile manager 634 of FIG. 6. Process 1000assumes that each node in a cluster has had the same update installerpackages installed and that those packages were installed in aconsistent manner. Accordingly, if the existing profile tool is enhancedto update the association between a profile and the runtime, and pushedout using the node agents to all nodes, then this association can beeasily done. A file, for example, inprofiles\AppSrv01\config\cells\cellName\nodes\nodeName\runtimeversion.xml could be introduced to store the association.

Process 1000 begins by starting the profile (Step 1002). Process 1000enables a user interface to setup the association between a profile anda runtime server instance at a particular version level (Step 1004).

Process 1000 identifies which version of the Enterprise applicationserver should be used to fulfill the request (Step 1006). Process 1000makes the identification based on a profile identifier, such as profileidentifier 636 of FIG. 6. A classpath that contains files from theselected version is constructed, and backfilled with any necessary filesfrom previous versions (step 1008). For example, a version 6.1.0.25 isindicated by the profile identifier. A version-base-6.1.0.0 is then usedto backfill version 6.1.0.25 with any necessary files not contained inversion 6.1.0.25. The required version is started (Step 1010), with theprocess terminating thereafter.

Thus, the illustrative embodiments provide a computer implementedmethod, a tangible storage medium, and a data processing system forbuilding a runtime environment of a system. A profile manager receives aservice request containing a profile identifier. The profile identifierspecifies a required version of at least one software component. Theprofile manager identifies a complete installation of the softwarecomponent, and at least one delta file. The profile manager dynamicallyconstructs a classpath for the required version by preferentiallyutilizing files from the at least one delta file followed by files fromthe complete installation. The runtime environment is then builtutilizing the classpath.

Illustrative embodiments provide a computer implemented method, systemand computer program product for an application/profile to select aruntime environment version during runtime. According to an illustrativeembodiment, an Enterprise application server fix pack upgrade functionslike a virtual installation and does not upgrade the Enterpriseapplication server version as a whole. Instead, both a current versionand the newer version should be present in the system after the upgradesuch that either version can be selected during application startup orthe profile startup phase.

According to a further illustrative embodiment, different runtimeversions, including the base version and upgraded versions are kept inthe system and are loaded dynamically based on the runtime election.

The matching of a profile to a runtime environment can be made by aprofile manager tool, or by editing some deployment descriptor at thetop of the profile. A corresponding profile on each node of the nodecluster may need to be matched to a corresponding runtime version oneach node of a cluster.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

The invention can take the form of an entirely hardware embodiment, anentirely software embodiment or an embodiment containing both hardwareand software elements. In a preferred embodiment, the invention isimplemented in software, which includes but is not limited to firmware,resident software, microcode, etc.

Furthermore, the invention can take the form of a computer programproduct accessible from a computer-usable or computer-readable mediumproviding program code for use by or in connection with a computer orany instruction execution system. For the purposes of this description,a computer-usable or computer readable medium can be any tangibleapparatus that can contain, store, communicate, propagate, or transportthe program for use by or in connection with the instruction executionsystem, apparatus, or device.

The medium can be an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system (or apparatus or device) or apropagation medium. Examples of a computer-readable medium include asemiconductor or solid state memory, magnetic tape, a removable computerdiskette, a random access memory (RAM), a read-only memory (ROM), arigid magnetic disk and an optical disk. Current examples of opticaldisks include compact disk—read only memory (CD-ROM), compactdisk—read/write (CD-R/W) and DVD.

A data processing system suitable for storing and/or executing programcode will include at least one processor coupled directly or indirectlyto memory elements through a system bus. The memory elements can includelocal memory employed during actual execution of the program code, bulkstorage, and cache memories which provide temporary storage of at leastsome program code in order to reduce the number of times code must beretrieved from bulk storage during execution.

Input/output or I/O devices (including but not limited to keyboards,displays, pointing devices, etc.) can be coupled to the system eitherdirectly or through intervening I/O controllers.

Network adapters may also be coupled to the system to enable the dataprocessing system to become coupled to other data processing systems orremote printers or storage devices through intervening private or publicnetworks. Modems, cable modem and Ethernet cards are just a few of thecurrently available types of network adapters.

The description of the present invention has been presented for purposesof illustration and description, and is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the art. Theembodiment was chosen and described in order to best explain theprinciples of the invention, the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

1. A computer implemented method for building a runtime environment of asystem, the computer implemented method comprising: receiving by aprocessor, a service request containing a profile identifier, whereinthe profile identifier specifies a profile to be used to create arequired instance of at least one software component needed to fulfillthe service request, wherein the required instance of the at least onesoftware component is a complete installed version of an applicationserver process in a particular runtime environment; identifying by theprocessor, from a database of profiles, a required profile thatspecifies a complete installation of the software component based on therequested profile identifier wherein the identified required profile isa data partition containing information associated with a completeinstallation of an application server process and all separatelyassociated delta files that update the required profile and areassociated to the profile; dynamically constructing by the processor, aclasspath for the required profile by preferentially utilizing filesfrom the at least one delta file first, and then followed by files fromthe identified required profile; and building by the processor, theparticular application server process utilizing the classpath andallocating the particular application server process within the runtimeenvironment.
 2. The computer implemented method of claim 1, wherein theat least one delta file further comprises a first delta file and asecond delta file, wherein the first delta file is an earlier update tothe complete installation, and wherein the second delta file is asubsequent update to the complete installation, wherein the step ofdynamically constructing a classpath for the required version bypreferentially utilizing files from the at least one delta file followedby files from the complete installation further comprises: applying by aprocessor, files and directories in the second delta file; responsive bya processor, to applying the files and the directories in the seconddelta file, applying files and directories in the first delta file; andresponsive to applying the files and the directories in the first deltafile, applying by a processor, files and directories in the completeinstallation.
 3. The computer implemented method of claim 1, wherein theparticular runtime environment comprises one of a plurality of runtimeenvironments in the system, each runtime environment being implementedin a separate instance of an object oriented program virtual machine. 4.The computer implemented method of claim 3, wherein ones of theplurality of runtime environments utilize different ones of the at leastone delta file, such that the ones of the plurality of runtimeenvironments have their own configuration files, logs, and properties.5. The computer implemented method of claim 1, wherein the runtimeenvironment comprises a object oriented program code runtimeenvironment, and wherein the classpath is specified by the logicallyoverlaying any of a plurality of object oriented program code softwarecomponents with object oriented program code classes specified in theuser profile at the required version, and wherein the profile identifierin the service request specifies required object oriented program codeclass version.
 6. The computer implemented method of claim 1, whereinthe profile identifier specifies the arrangement hierarchy for logicallyoverlaying the complete installation of the software component, and theat least one delta file.
 7. The computer implemented method of claim 1,wherein the complete installation of the software component is acomplete installation of an enterprise application server.
 8. Thecomputer implemented method of claim one, wherein the at least one deltafile further comprises a first delta file and a second delta file,wherein the first delta file is an earlier update to the completeinstallation, and wherein the second delta file is a subsequent updateto the complete installation, the method further comprising: receivingby the processor, the service request containing the profile identifier,wherein the profile identifier specifies the required version of the atleast one software component, wherein the required version is a patchedversion of the complete installation consisting of the completeinstallation in the first delta file; responsive to receiving theservice request containing the profile identifier wherein the profileidentifier specifies the required version of the at least one softwarecomponent, wherein the required version is the patched version of thecomplete installation consisting of the complete installation in thefirst delta file, applying files and directories in the first delta filewithout applying files and directories in the second file; andresponsive to applying the files and the directories in the first deltafile, applying by the processor, files and directories in the completeinstallation.